Roadmap 6.1.2 (PR #340) merged to main during this branch's draft and was
picked up by a rebase. It added a reusable nested clap tree
(NestedFixtureConfig) to the existing orthohelp_fixture crate and established
the --root-type multi-root convention, but covers only IR, roff, and
PowerShell — not the agent-context format.

Revise the plan to reuse that infrastructure instead of authoring new fixture
crates: reuse NestedFixtureConfig (nested) and FixtureConfig (enum, the default
root), and add only a minimal SimpleFixtureConfig root, each golden selected via
--root-type. Narrow Risk 1 (the agent-context recursion is now the only
unexercised part), reduce scope (one struct plus locale keys, no new workspace
members), and add a 6.2.2-vs-6.1.2 render-assertion fence. A revision note
records the change.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Update the 6.2.2 ExecPlan to record D1, D2, D3, and D5 as
accepted, and choose the D4 pre-1.0 enum casing change.

Keep Milestone 1 and the compatibility-policy work aligned with the
new decision to standardize agent-context enum wire strings to
`snake_case` before locking the schema.

Record the execution start for the 6.2.2 ExecPlan, including the
current branch, PR title, and Lody session context.

Standardize agent-context enum serialization on `snake_case` before
locking the v1 wire contract. Add schema guard tests for the version
and kind pins, comprehensive wire shape, unknown-field tolerance, and
variant-exhaustive enum wire values.

Record the Milestone 1 red/green evidence and gate results in the
ExecPlan so later milestones can rely on the locked schema baseline.

Add generator-side guards for the agent-context transform before expanding the
end-to-end golden matrix. The adapter now normalizes unstable proc-macro token
spacing in default displays, so default-bearing goldens are not churned by
`proc_macro2` formatting changes.

The new tests prove deterministic pretty JSON output for the same bridge IR and
pin nested command projection through a two-level command tree. The existing
agent-context golden is re-baselined for the approved default-display
normalization.

Cover agent-context generation for the three root shapes named by the plan:
a minimal flat scalar root, the existing enum-bearing fixture root, and the
nested command-tree fixture from 6.1.2. The golden test is now parametrized over
root types and snapshots each shape independently.

Add a nested BDD scenario that asserts generated command paths include both a
top-level subcommand and the deeper admin audit path, proving the behaviour
layer exercises nested agent-context output rather than only checking that JSON
was written.

Treat `--format all` as additive over the now-locked agent-context contract by
writing `agent-context.json` alongside the existing IR, man-page, and
PowerShell artefacts. This fulfils the previous deferral without changing the
legacy output paths or assertions.

The all-formats BDD scenario now checks that the compact agent-context document
is emitted in addition to the existing generated outputs.

Record the v1 compatibility rules, defaulting policy, and
agent-context inclusion in format-all documentation.

Record the skill_manifests default added on main in the simple and nested agent-context snapshots after rebasing onto origin/main.